約 6,146,469 件
https://w.atwiki.jp/ketcindy-eng/pages/24.html
Modified Sep. 1st 2016 Setting up KeTCindy in case when all software are installed for the first time Firstly, download and ungzip "InstallforMac" and "KeTCindy" onto your Desktop. 1) Copy InstallforMac.dmg and ketcindy.zip to Desktop. 2) Unzip ketcindy.zip and Double click InstallforMac.dmg to make the disk image. 3) Installing TeX Open installforMac, and copy kettex forlder into "/Applications/KeTCindy". 4) Installing Scilab5.5.2 Extract "scilab-5.5.2-x86_64.dmg" by double clicking and put the resulting "Scilab-5.5.2" into /Applications. Rmk You don t need any java upgrade only for KeTCindy. 5) Installing Cinderella2 Copy "Cinderella2.zip" and paste it into desktop. Extract it by double clicking and put into /Applications. Rmk In case when the warning "There is no Java" appears, update Java. 6) Setting up KeTCindy (a) Copy ketcindy folder into /Users/(name)/ (b) Double click "template.cdy", then Cinderella2 will launch. (c) Choose "Reveal Plugin Folder" from "Script" menu. (d) Paste a file KetcindyPlugin.jar in ketjava into folder "Plugins". (e) Close Cinderella2 once. RMK Don t delete the folders and files originally contained in "Plugins". 7) Use of CindyScript (1) Open "tmplate.cdy" in "KeTCindy" in your home directory by double clicking. (2) Choose "Scripting"= "Edit Cindyscript" from top menu. (3) In the slot "draw"= "figures", generate and modify figures. (4) Push the GEAR mark in the top menu. 8) Push "Texview" and "Exekc" button sequentially. Then, Scilab and TeX are succesively executed, and the final PDF output is displayed. 9) If you use texworks as a editor of TeX, (1) Launch TeXworks, and choose Edit Preference Typeset (2) Set as follows Push + name texworkslatex program find; /Applications/kettex/ketbin/texworkslatex.sh Argument $fullname
https://w.atwiki.jp/apache_reading/pages/23.html
server/protocol.c static apr_status_t buffer_output(request_rec *r, const char *str, apr_size_t len) { conn_rec *c = r- connection; ap_filter_t *f; old_write_filter_ctx *ctx; if (len == 0) return APR_SUCCESS; /* future optimization record some flags in the request_rec to * say whether we ve added our filter, and whether it is first. */ /* this will typically exit on the first test */ for (f = r- output_filters; f != NULL; f = f- next) { if (ap_old_write_func == f- frec) break; } if (f == NULL) { /* our filter hasn t been added yet */ ctx = apr_pcalloc(r- pool, sizeof(*ctx)); ap_add_output_filter("OLD_WRITE", ctx, r, r- connection); f = r- output_filters; } /* if the first filter is not our buffering filter, then we have to * deliver the content through the normal filter chain */ if (f != r- output_filters) { apr_bucket_brigade *bb = apr_brigade_create(r- pool, c- bucket_alloc); apr_bucket *b = apr_bucket_transient_create(str, len, c- bucket_alloc); APR_BRIGADE_INSERT_TAIL(bb, b); return ap_pass_brigade(r- output_filters, bb); } /* grab the context from our filter */ ctx = r- output_filters- ctx; if (ctx- bb == NULL) { ctx- bb = apr_brigade_create(r- pool, c- bucket_alloc); } return ap_fwrite(f- next, ctx- bb, str, len); }
https://w.atwiki.jp/icabmobilemodule/pages/15.html
このページは http //www.icab.de/blog/2010/02/17/modules-for-icab-mobile/ の日本語訳をつける作業ページです。ページを編集 「この日本語訳おかしくね？」と思ったら 超意訳ですが、ざっくり意味が伝わればそれでオーケーぐらいのスタンスです。 細かいことには目をつむってください ここにコメントをどうぞ autorun機能についての追記を翻訳 -- 管理人 (2010-08-02 20 22 04) postRequest関数についての追記を翻訳 -- 管理人 (2010-08-23 10 51 36) titleの訳せていないかったところを翻訳 -- vmeniv (2011-01-01 16 24 23) モジュールのvarプロパティにappinstalledが増えました。ほかのアプリと連携させるモジュールに使えます。また、プラットフォームで分岐もでき、「navigator.platform == "iPad"」でiPadかどうかわかるみたいです。（ソースは元から入っているOpenInGoodreader.icabmodule) -- 名無し (2011-10-20 00 19 17) ×appinstalled、○installed -- 名無し (2011-10-20 00 24 25) 名前 コメント Modules for iCab Mobile (Updated) The version 2.1 of iCab Mobile introduces a new “modules” feature. Modules make it possible to add new features in iCab Mobile just by downloading them. They can be used for simple things like increasing the font size so a page is more easy to read on the small iPhone screen, but also more complex tasks can be done, like downloading YouTube videos or to post a web page URL at Twitter (including the login and creating a tiny URL). iCab Mobile 2.1 comes with a few built-in modules, and there are also several modules available for download. バージョン2.1以上のiCab Mobileにはモジュールという機能が備わっています。モジュールによってiCab Mobileは、それらをダウンロードするだけで新たな機能を追加することができます。モジュールはiPhoneの小さなスクリーンでも読みやすくするためにフォントを大きくする、といったシンプルなことにも使えますし、もっと複雑な、たとえばYouTubeからビデオをダウンロードしたりウェブページのURLをTwitterでつぶやく(ログインや短縮URL作成ももちろん含む)、といったこともできます。 iCab Mobile 2.1にはいくつかのモジュールを内蔵していますし、ダウンロード可能なさまざまなモジュールが存在します。 This blog post will explain, how you can write your own modules for iCab Mobile and how you (and maybe other users) can install them in iCab Mobile. このブログ記事では、あなたがどのようにしてモジュールを書けばいいか、またどのようにしてインストールするかを説明しています。 技術的背景 (Technical background) Technically, modules are somehow similar to bookmarklets, but with more features and more flexibility. This means the modules are written in JavaScript code and they can do everything that can be done with JavaScript. Unlike bookmarklets, where the complete JavaScript code must be squeezed in one single line so that it can be used as a URL with “javascript” scheme, the modules can be nicely formatted, without any line limitation. Modules have a special header section where the module properties are defined. The properties include an icon that is displayed in the Modules panel of iCab Mobile, but also settings which do allow the user to configure the module in the iCab Mobile module settings panel. 技術的にはモジュールはブックマークレットと似ていますが、より機能的でより柔軟です。それは、モジュールはJavaScriptで書かれており、JavaScriptで可能なことはすべて可能だという意味でです。ブックマークレットと違うのは、ブックマークレットはjavascriptスキームのURLとして扱われるためにスクリプトをまるごと一行に圧縮しなければなりませんが、モジュールは複数行の見やすいフォーマットでよい点です。モジュールはモジュールのプロパティを定義する特殊なヘッダーセクションを持ちます。プロパティにはiCab Mobileのモジュールパネルに表示されるアイコンや、ユーザがiCab Mobileの設定パネルから変更することができる設定などがあります。 モジュールの構造 (The module structure) The module is a normal text file with JavaScript code. There’s a header section and the code section. Here’s an example, how this looks like モジュールはJavaScriptのコードが書かれた普通のテキストファイルです。ヘッダーセクションとコードセクションが存在します。サンプルを下に示します //startconfig //id=de.icab.crazy //icon=iVBORw0KGgoAAAANSUhEUgAAACwAAAAkCAYAAADy19hsAAAWrGlDQ1BJQ0... //title=Crazy Layout //description=The module sets random colors for the page elements //description.de=Das Modul setzt alle Farben der Seite auf Zufallswerte //var=confirmation;type=confirmation;default=false; //var=language;type=language; //endconfig var hex = "0123456789abcdef"; function iCabMobileGoCrazyForElement(element) { if (element.nodeType == 1) { if (element.style.display != "none" element.nodeName.toLowerCase() != select ) { element.style.backgroundColor = "#" + hex.charAt(Math.random()*16) + hex.charAt(Math.random()*16) + hex.charAt(Math.random()*16); element.style.color = "#" + hex.charAt(Math.random()*16) + hex.charAt(Math.random()*16) + hex.charAt(Math.random()*16); for (var i=0; i element.childNodes.length; i++) { iCabMobileGoCrazyForElement(element.childNodes[i]); } } } } var doAction = (confirmation == false); if (confirmation) { var text = "Go crazy?"; doAction = confirm(text); } if (doAction) { iCabMobileGoCrazyForElement(window.document.body); } The header section defines the properties of the module. The header section starts with the line ヘッダセクションではモジュールのプロパティを定義します。ヘッダセクションはこの一行から始まります //startconfig and ends with the line 終わりはこの一行です //endconfig Between these two lines all the properties are defined, each individual property definition occupies exactly one line, so currently you can’t split the definition of a property into multiple lines. Also no empty lines are allowed in the header section. Each property definition has the following format この二行の間にすべてのプロパティを定義し、それら個々のプロパティ定義は一行ごとに解釈されます。(訳注※ひとつのプロパティごとに一行ということ。)そのため、複数行にわたる内容の定義はできません。また、空行は含んではいけません。どのプロパティも以下のようなフォーマットになります //property=value;additional paramaters (additional paramaters = 追加パラメータ) The additional parameters are optional and not always needed or required. 追加パラメータはオプションであり、いつも必要なわけではありません。 There are some properties which are required. If they are missing, iCab Mobile will ignore the module. Other properties are optional and do not need to be present. Here are the properties which are currently supported いくつかのプロパティは必須です。もしそれが間違っていたら、iCab Mobileはそのモジュールを無視します。(インストールされません。) その他のプロパティはオプションなのでなくても動作します。ここに現在サポートしているプロパティを挙げます id (required[必須]) This property identifies the module. When updating or reinstalling a module, the value of the “id” will be used to find the old module that has to be replaced by the new one. So when updating a module, you must not change the value of the “id”. Everything else can be modified, even the name of the module. The value of the “id” property should be unique among all existing modules. The best way to find a good “id” value is to use a reverse domain name appended with the module name. If your own web page has the domain “www.your-domain.com” you should set the “id” value to “com.your-domain.moduleName”. All of your own modules will have the same reverse domain prefix and the module name as suffix. If you don’t have your own domain, you can use your name and city as a prefix and maybe some random numbers, anything which makes it unlikely that someone else uses the same id value. The “id” is not visible to the user within iCab Mobile. Its only used to identify the module. このプロパティはモジュールを識別するためのものです。モジュールをアップデートや再インストールするときにこの"id"の値が、新しいものに置き換える必要のある古いモジュールを見つけるときに使用されます。ですからモジュールをアップデートするときに、この"id"の値を変更してはいけません。そのほかなら何を変えても構いません、モジュールの名前でさえ。このidというプロパティは、この世に存在する他のすべてのモジュールとかぶらないユニークなものである必要があります。良いidを見つけるベストな手段として、ドメイン名をひっくり返しモジュール名を足して使うという手があります。もしあなたが"www.your-domain.com"というドメインをあなたのウェブページに使っているならば、あなたはidに"com.your-domain.moduleName"を使うべきでしょう。あなた作ったすべてのモジュールは、ひっくり返したドメイン名を接頭辞に、モジュール名を接尾語に持つということになります。もしあなたがドメインを持っていないならば、あなたは接頭辞にあなたの名前や都市の名前にいくつかのランダムな数字(不幸にも同じidを持ってしまわないために)を足して使うといいでしょう。idはiCab Mobileのユーザの目に触れることはありません。モジュールの識別のためだけに使用されます。 Example 例 //id=de.icab.crazy or if you don’t have your own domain, you may use something like this もしドメインを持ってないならば、例としてはこんな感じです //id=de.darmstadt.clauss.alexander.crazy //id=ja.saitama.taro.yamada.crazy title (required[必須]) The title defines the name of the module and is displayed within the modules settings of iCab mobile. The title property is needed so that the user can enable or disable the modules in the in-app settings and also configure the modules settings. titleでモジュールの名前を定義します。iCab Mobileのモジュール設定で表示されるものです。タイトルプロパティはユーザがアプリ内設定でモジュールを有効化/無効化するときやモジュールの設定をするときのために必要です。 Example 例 //title=Crazy Colors You can also define localized versions of the title. Just append the language code (for example “en” for English, “de” for German, “it” for Italian etc.) of any of the languages which are supported by the iPhone OS to the “title” keyword あなたはローカライズされたタイトルを定義することができます。iPhone OS がサポートする言語の言語コード(たとえば英語なら"en", ドイツ語なら"de", イタリア語なら"it")を"title"という語の後につけるだけです (日本語はjaですが、日本語が使えるのかどうかは未確認です) like this こんな風に //title.de=Verrückte Farben //title.ja=狂った色 This way you can easily localize the module in many languages. The key “title” without a language code appended will be used as default language which is used when none of the defined languages does match the current language of the iPhone or iPod Touch. この方法で、簡単にモジュールを多言語にローカライズできます。言語コードのついていない「title」というキーは言語コードが現在の[デバイス]の言語に適合する定義済みの言語コードが無かったときに使われる既定の言語として使用されます。 In general the default language should be English. If no default language is defined, then the very first language that is define will be used as default language. But it is highly recommended, that you simply use English as the default language (without language code). 一般には既定の言語は英語であるべきです。もし既定の言語が定義されていないときは、一番最初に定義されている言語が既定の言語として使われますが、既定の言語（言語コードの無いtitleキー)として英語を使うことが大いに推薦されます。 So if the module supports English and German, the title would be defined this way ですので、もしモジュールが英語とドイツ語をサポートするのであれば、titleは次のように定義されます //title=Crazy Colors //title.de=Verrückte Farben description (optional[オプション]) The description is displayed in the settings panel of the module in iCab Mobile. The description should explain what the module is doing. Localizing is done in the same way as described above for the title. Append the language code to the “description” keyword descriptionはiCab Mobileのモジュール設定パネルで表示されます。descriptionはモジュールが何をするものなのかの説明がよいでしょう。titleプロパティと同様の手段を用いて次のようにローカライズが可能です //description=The module sets random colors for the page elements //description.de=Das Modul setzt alle Farben der Seite auf Zufallswerte icon (optional, but highly recommended[オプションだが強く推奨]) The icon is displayed when the user opens the modules panel where the modules can be activated by tapping on their icon. The icon should be an image file in PNG or JPG format. The data of the image file must be encoded with “base64″ and this “base64″ encoded data can be then used as value for the “icon” property. Usually the base64 data is formatted in lines of at most 64 characters length, but for the modules, all line breaks must be removed, so the icons data can be completely included in one line. The size of the module icons (the visible part) should be approx. 41*32. You can use the following empty icon image as a template for your own icons iconはユーザがモジュールのアイコンをタップすることによってそのモジュールを動作させることができるモジュールパネルを開いたときに表示されます。iconはPNGかJPGフォーマットの画像ファイルです。画像ファイルはBase64でエンコードされている必要があり、このBase64でエンコードされたデータをiconプロパティに指定します。通常、Base64データは64種類の文字からなる複数行で成りますが、モジュールに組み込むにあたり、改行を削除し一行にする必要があります。モジュールのアイコンは41*32が推奨されます。あなたのアイコンを作るにあたって空のアイコンイメージを用意したので使ってください http //www.icab.de/img/empty.png (iCabが用意した空のボタン画像) //icon=iVBORw0KGgoAAAANSUhEUgAAACwAAAAkCAYAAADy19hsAAAWrGlDQ1BJQ0... var The “var” property defines JavaScript variables, which are initialized by iCab Mobile. These variables can be used to allow the user to configure the modules, but also to get certain system properties, like the system language. "var"プロパティはiCab Mobileによって初期化されるJavaScriptの変数を定義します。これらの変数はユーザがモジュールの設定として変更することができ、またそれだけでなく、システム言語のようなシステムプロパティを得ることもできます。 Variables do have the following format 変数は次のような形式をとります //var=NameOfVar;type=typeOfVar;default=defaultValue;title=labelForSettings; iCab Mobile will create a standard JavaScript variable declaration and initialization for all of these variable properties and adds these to the JavaScript code of the module. So your JavaScript code of the module can check and use these variables just like any other variables. iCab Mobileはこれら変数プロパティをJavaScriptから利用するために変数宣言と初期化をするJavaScriptコードを生成し、モジュールのJavaScriptコードに追加します。 そのため、それらはJavaScriptの変数であるため、特別な利用方法などいらず普通の変数として扱うことができます。 The value of the “var” property is the name of the variable. "var"プロパティの値は変数の名前となります。 The “title” property is required, when the variable should be presented to the user in the module settings, so the user can change the value of the variable. The value of the “title” property is used as the label in the settings panel. You can add additional localized versions of the title, just by appending the language code (as described above). "title"プロパティはユーザがモジュール設定にて変更可能であるときに必要で、これによってユーザは変数の値を変更することができます。"title"プロパティの値は設定パネルのラベルにて使用されます。言語コードを付加すればローカライズされた表示をすることも可能です。 The “default” property can be used to define a certain default value for the variable. "default"プロパティで変数の規定値を定義することができます。 The value of the “type” property is the type of the variable, which can be one of the following "type"プロパティは変数の型で、次のうちのひとつをとることができます bool or boolean 真偽型 The variable can have the values true or false. In the module settings this variable will be represented by a “switch” control. If the user switches it on, the variable will have the value true otherwise the variable will have the value false. The title attribute is required for this type. The title is shown as label for the switch in the module settings. trueかfalseの値をとる真偽値型です。モジュール設定でスイッチコントロールによってユーザによる状態変更が可能です。この型にはモジュール設定でラベルとして表示するための"title"プロパティが必要です。 int or integer 数値型 The variable can have a numerical value. In the module settings, this variable is represented with a text field where you can enter digits. The title attribute is required for this type. The title is shown as label for the edit field in the module settings. 数値型です。モジュール設定では数字しか入力できないテキストフィールドによってユーザによる数値の変更が可能です。この型にはモジュール設定でラベルとして表示するための"title"プロパティが必要です。 string or text 文字列型 The variable can have a string value. In the module settings, it is represented as a text field. The title attribute is required for this type. The title is shown as label for the edit field in the module settings. 文字列型です。モジュール設定ではテキストフィールドによってユーザによる文字列の変更が可能です。この型にはモジュール設定でラベルとして表示するための"title"プロパティが必要です。 pass or password パスワード文字列型 The variable can have a string value. In the module settings, it is represented as a text field where the input is hidden. The title attribute is required for this type. The title is shown as label for the edit field in the module settings. パスワード文字列型です。セキュリティのために入力した文字列が隠される点を除いて、文字列型と一緒です。この型にはモジュール設定でラベルとして表示するための"title"プロパティが必要です。 lang or language システム言語コード型 The value of this variable is a string that contains the language code of the currently selected system language. This variable is not presented in the settings panel of the module. Therefore no title property is required here. システムの既定の言語の言語コードが代入される文字列型です。"title"プロパティは不要です。"en", "de", "it", "ja"といった値をとります。 confirm or confirmation 確認ダイアログ設定型 The variable has a boolean value. It is represented in the module settings by a switch where the user can enable or disable a confirmation box. If enabled, iCab Mobile will ask each time the module is activated, if it should be really executed. This variable does not need a “title” property because it is automatically localized within the module settings panel. 確認ダイアログ設定が代入される真偽型です。モジュール設定でできる確認ダイアログを有効にするか無効にするかの設定がどうなっているかを提供します。もし有効にされているなら、iCab Mobileはモジュールが作動するときに毎回本当に実行するかどうかを訪ねます。この変更オプションはiCab Mobileによって提供され自動的にローカライズされるので、この変数には"title"プロパティはいりません。 autorun 自動実行 The variable has a boolean value. It is represented in the module settings by a switch where the user can configure, if the module should be automatically run when the page has finished loading. This variable does not need a “title” property because it is automatically localized within the module settings panel. If there’s no variable of the type “autorun” set, the module can only be opened manually. You can set the default value for the variable to switch on or off the “autorun” feature for the module. But the user will be always able to disable the “autorun” feature in the module settings. When the modul is executed, the variable that is defined with the type “autorun” will have the value “true” if the module was executed automatically (which means when the page has finished loading) and the value “false” if the module was opened manually by the user. So a module is able to do different thing when called automatically and when called manually (for example it can mark elements when called automatically to notify the user about something, and modify the elements when called manually, to do the real work). [This feature will be available in iCab Mobile 3.3, it s not yet available in version 3.2] この変数は真偽値を持ちます。もしページロード完了時にモジュールが自動的に起動されるように推奨される場合、モジュール設定にあるユーザが設定することができるスイッチが提供されます。この変数には"title"プロパティは必要ありません。勝手にローカライズされます。もし"autorun"変数が定義されていない場合、モジュールは手動によってのみ起動できます。あなたはあなたのモジュールにおける"autorun"機能のデフォルトの設定をオン、オフのどちらにも設定することが出来ます。しかし、ユーザはいつでも"autorun"機能を停止することができます。モジュールが実行されたとき、autorun型の変数は自動実行されたとき(つまりページロード完了時にiCab Mobileがモジュールを起動させたとき)は"true"、もしくはユーザによって手動起動されたときは"false"の値をとります。なのでモジュールは自動実行と手動実行のときで別々の振る舞いをすることができます。[この機能はiCab Mobile 3.3から利用可能になります。バージョン3.2では利用不能です] select 列挙型 The variable of this type can be used to select one item from an array of items. This variable type uses the title property in the same way as the other types to define the label in the module settings. ようするに列挙型です。ラジオボタンの方が近いかもしれません。"title"プロパティを設定すればモジュール設定で反映されます。 This variable type requires that two other properties are defined as well. The “values” property must be defined to create the array of values the user can choose from, and the “valuetitles” property must be defined to define the array of titles for these values. The “valuetitles” properties is localizable again, so append the language code as shown above for the “title” property. For the “values” and “valuetitles” property, all items must be separated by the “|” character. この変数では後述する二つのプロパティが定義されている必要があります。"values"プロパティはユーザが選んだ項目がとる値の配列で、"valuetitles"プロパティはユーザが選ぶ項目名の配列です。"valuetitles"プロパティもまた、"title"プロパティと同じように言語コードをつければローカライズすることができます。"values"と"valuetitles"プロパティは項目を区切るために"|"で区切る必要があります。 An example 例 //var=s;type=select;valuetitles=One|Two|Three;values=1|2|3;title=Number;default=2 //var=j;type=select;valuetitles=壱|弐|参;values=1|2|3;title=数値;default=2 In the settings the user would be able to choose between “One”, “Two” and “Three”. If the user selects “One” the variable s would have the value 1, if the user selects “Two” the variable s would have the value 2 etc. The default value would be 2 and the user would see that “Two” is preselected. The whole setting would have the label “Number”. この設定の場合、ユーザは"One" "Two" "Three"のうちからひとつを選ぶことができます。もしユーザが"One"を選んだなら変数の値は 1 になり、もし"Two"を選んだなら 2 になる、とっった具合です。"default"によって変数は 2 に、最初から"Two"を選んだ状態になります。このラジオ選択自体に"title"でラベルをつけることができます。 When the user activates a module, iCab Mobile will process the header sections and creates JavaScript variable declarations for all the variable definitions from the header section. The values for these variables will be determined by the module settings. Technically, iCab will add these variable declarations before the JavaScript code section of the module, so the module can access these variables. These variables and the JavaScript code section will be embedded in a block, so they have their own scope and do not interfere with the JavaScript code and variables which are already present in the web page. ユーザがモジュールを動作させるとき、iCab Mobileはヘッダーセクションを読み込み、ヘッダーセクションのすべての変数定義のためにJavaScriptコードを作り出します。それらの変数の値はモジュール設定によって決定されます。技術的には、iCab Mobileはそれらの変数宣言をモジュールのJavaScriptコードセクションの前に追加するので、それによってモジュールがそれらの変数にアクセスできるようになります、それらの変数やJavaScriptコードセクションはブロックに組み込まれて実行されるため、現在表示しているウェブページのスコープを汚すことはありません。 This means, when the module looks like this それはつまり、以下のモジュールを例に考えると //startconfig //id=de.icab.module //icon=iVBORw0KGgoAAAANSUhEUgAAACwAAAAkCAYAAADy19hsAAAWrGlDQ1BJQ0... //title=Some Module //var=confirmation;type=confirmation;default=false; //var=language;type=language; //var=text;type=string;title=Text; //endconfig function DoSomething() { // here s the actual code which is doing all the work of the module // ここにモジュールの実際のコードを書きます } if (confirmation) { //doAction = confirm("Really activate the module?"); doAction = confirm("本当にこのモジュールを実行しますか?"); } else { doAction = true; } if (doAction) { DoSomething(); } the resulting code that is actually executed in the context of the web page looks like this 実際に実行されるコードはこのようになります { var confirmation = true; var language = "en"; var text = "User Input"; function DoSomething() { // here s the actual code which is doing all the work // ここにモジュールの実際のコードを書きます } if (confirmation) { //doAction = confirm("Really activate the module?"); doAction = confirm("本当にこのモジュールを実行しますか?"); } else { doAction = true; } if (doAction) { DoSomething(); } } JavaScriptの特別関数 (Special JavaScript functions) Modules can also call special JavaScript functions, which are defined by iCab Mobile to do certain tasks. モジュールはiCab Mobileによって定義された特殊な関数を呼ぶことができます。 There are the following functions available 次のような関数が利用可能です startDownload(url,file) This function starts a download. The parameters are the URL and a suggestion for the filename under which the download should be saved. この関数はダウンロードを開始します。引数はURLと保存されるファイル名です。 postRequest(url,content,”callBackFunction”) new!! This function gets the data from the URL using the HTTP POST command (posting “content” to the server) and then passes the HTTP status code and the data to a function called “callBackFunction” (see getRequest() below for a description of the callback function). この関数はHTTPのPOSTコマンド(”content”をサーバにポスト)でデータを取得し、HTTPステータスとデータを引数にコールバック関数を呼びます。(コールバック関数に関しては下のgetRequest()関数の説明をご覧ください) getRequest(url,”callBackFunction”) This function gets the data from the URL (using the HTTP GET command) and then passes the HTTP status code and the data to a function called “callBackFunction” (the second parameter is a string with the name of the callback function that must be implemented by the Module to process the data) この関数は指定されたURLからHTTPのGETコマンドを使ってデータを取得し、HTTPステータスとデータを引数にコールバック関数を呼びます。(二番目の引数はモジュール内で実装されたコールバック関数の関数名の文字列です) function callBackFunction(status, data) { // "status" is an integer value with the HTTP status code (200, 404, etc) // "data" is a string with the URL data // "status"はHTTPステータスコードの数値です // "data"は取得したデータ(文字列)です } モジュールのインストール (Installing the modules) Installing the modules is done by simply downloading them from a web site. So all you need to do is to provide a web page which contains a link to your module. The link URL must use the URL scheme “icabmodule” or “javascriptmodule” instead of the usual “http” scheme. This is how iCab Mobile detects that it should download and install a module. モジュールをインストールは、ウェブサイトからダウンロードするだけです。ですからあなたがすべきことはモジュールへのリンクが含まれるウェブページを用意するだけです。モジュールへのURLは、通常の"http"スキームの代わりに "icabmobule"スキームか"javascriptmodule"スキームを使ってください。 For example, if your module can be accessed with the URL http //your.webspace.com/modules/TheModule.icabmodule the HTML link you would have to include in your web page would look like this たとえば、もしあなたのモジュールに次のURLでアクセスできるとしたら http //your.webspace.com/modules/TheModule.icabmodule あなたがウェブページに盛り込むべきHTMLのリンクは次のようになります a href="icabmodule //your.webspace.com/modules/TheModule.icabmodule" Download TheModule /a or alternatively look like this あるいは、次のようにします a href="javascriptmodule //your.webspace.com/modules/TheModule.icabmodule" Download TheModule /a If you include these links on a web page which is accessible to other people as well, other iCab Mobile users would be also able to install your module. So you can easily share your modules with other users. もし、誰もがアクセスできるウェブページにこれらのリンクを組み込んでいるのであれば、ほかのiCab Mobileユーザも同じようにあなたのモジュールをインストールすることができます。 ですからあなたは簡単にあなたのモジュールをほかのユーザーとシェアすることができます。 I’ve created two URL schemes for the modules. In case other iPhone developers are interested in this module feature (candidates would be developers of other iPhone browsers), it would be great if all these modules would be compatible. 我々はモジュールのために二種類のURLスキームを用意しました。ほかのiPhoneデベロッパー(とくにiPhoneのウェブブラウザ開発者)がこのモジュール機能に興味をもってくれた場合、すべてのモジュールが互換性を持っているならすばらしいでしょう。 In this case the general URL scheme “javascriptmodule” could be used by all the Apps supporting the modules feature. And the other URL scheme could be used for application specific-modules (so “icabmodule” would be only accepted by iCab Mobile). Just a reminder My AppLink Proposal can be also used by other iPhone Apps. この場合において、"javascriptmodule"スキームはモジュール機能をサポートするすべてのアプリに使われます。もう一方は、特化したモジュール(つまり、"icabmodule"スキームはiCab Mobileしか受け付けません)に使われます。 You can also sent the module to me so I can include it into the modules download page, which is accessible through the “Download” module that is built-in in iCab Mobile. This way the module can be immediately found by all iCab Mobile users. あなたはモジュールを私(訳注※iCab Mobileの作者)に送ることができ、そうすれば私はそれらのモジュールをiCab Mobileに元から入っている"Download"モジュールを通してアクセス可能なモジュールダウンロードページに取り入れます。この方法ならすべてのiCab Mobileユーザがモジュールを即座に発見することができるでしょう。
https://w.atwiki.jp/chex/pages/320.html
Lecture for intermediate Lecture for intermediate Lecture for those who intend to become intermediate Lecture for those who intend to become intermediate Introduction As you, designers who are familiar to the development of OKEs some degree, may know that clear goals are not exist in this game. You can play it in any direction, and it is free that how far you elaborate. It can be thought that, the goal setting is also a part of the contents of this game already. That is, as you become more familiar, how to enjoy and how to beat becomes more different from each other. For example, there are some people pursue every day how well avoid mines. But next to it, there are some people do everything in their power to assault by destroying all mines. Descriptions satisfy both at the same time is extremely difficult. As you become more familiar, as it becomes finer contents, your own strategy is going to be made. For these reasons, it is difficult to determine what to lecture for intermediate people or what is the definition of intermediate in the first place. So first, for those who intend to become intermediate, I entered from the description of the timing and execution speed of the program that are essential knowledge for creating large programs. For the reaction rate of OKE and scale of the program A CPU that you select in Hardware has parameters of "storage capacity", "execution speed" (and weight). "Execution speed" represents the execution speed of the program and the unit c/s means "(the number of executing) chips per second". The highest execution speed of CPU is 240c/s; you can execute 240 actions or decisions per second. Looks ridiculously large numbers at first glance, but is not really so much. Let s take a closer look. In this game, various judgment of combat takes place on a frame-by-frame basis. Frame is a still image that makes up a video. When you choose "frame advance" of the system menu in combat you can check the status of frame-by-frame. This game is 30fps, 30 pictures will be displayed per second. Therefore, if the CPU is 240c/s, you execute 240 chips per one second (= 30 frames), 8 chips per frame (= 1/30 sec). To pause during the battle actually, you can check the number of executing chips that appears bright. This number will significantly affect the "reaction rate of OKE". OKE runs all the actions as instructed in chips read in that time. Even though you made an excellent program, not only it becomes waste unless it is done when it is needed, but also it may cause trouble when it is executed with unnecessary timing. So let s look at an avoidance decision. There is a branch of “whether there is a bullet around the body” at the beginning of the avoidance decision, perform the avoidance maneuver If this were yes, go to the next process if it was no. What is needed in this case is that the first branch is executed when there is a bullet in the vicinity of the body. For example, if you set the range of around the body radius 100m, it is best to branch to avoidance decision with a margin of distance of 100m. But if the code is longer, for example, what happens if a program executes about 40 chips until return at earliest? Even with the fastest CPU, it takes 5 frames or more to go around once. If there is only once decision per go-around, avoidance maneuver is performed 5 or more frames late when a bullet comes at the worst timing. 5 frames = 5/30 of a second, it is about 0.17 seconds. During this time, AP ammunition flies about 50m; beam and rail gun flies about 80m. That is, then you will get a direct hit with no reaction if it was shot from the distance. Even though you perform reaction, if not even 30m away at that time, it is too late to act. Leaving aside one shot of beam gun, in case of rail gun, even a hit is directly linked to defeat frequently. The avoidance decision was given as an example here, but I can say the same thing to the decision of all of course. As it become a larger-scale program, more complex assessment of the situation and actions can be performed by OKEs but the reaction rate will reliably drop instead. Stack of subtle reduction of reaction rate affect more than a little on combat result. If you create a large program without thinking about the reaction rate, most will weaken comprehensively than small and medium-sized programs. There are mainly two know-hows to maintain the reaction rate when you building a large program, utilizing subroutine and utilizing loop. Utilize subroutine In the CPU with a maximum storage capacity, there are two areas that can be form subroutines of 7× 7 size on the right side. It is possible to run the subroutine from the chips of the “SUB 1” “SUB 2” placed in the main program of the left side. When the executed subroutine is completed, the process proceeds to the next of “SUB” chip which was placed in the main routine. By placing regularly this "SUB" chips in the main routine, it becomes possible to execute programs implemented into the subroutine several times until go around a main routine. For example, implement avoidance decision into a subroutine, when you call the subroutine whenever the main routine proceeds about 10 chips, reaction rate is significantly improved because it began to determine once per about two frames whether it is necessary to avoid. It should be noted that, of course main program is stopped at the place of "SUB" chip while executing subroutine. If there is a long program that is always executed in the subroutine, the rotation of the main program will be dull depending on the number of calls. Although rate of behavior that implemented into the subroutine improves, all other actions are delayed slightly. Therefore, you must be sure to execute subroutines only when necessary. To give avoidance as an example, if the OKE is quick moving or jumping already, it is not needed to execute subroutine. By increasing the rotation speed of the main routine even slightly by reducing unnecessary processing, let s improve the rate of each operation. Utilize loop To tell the truth first, loop may cause a fatal bug in high probability if you are not familiar. What is the loop, about the risk and the usefulness of the loop, I describe a simple example together. Please see the image below. This is avoidance decision of the program that is described in "Lecture for beginners", introduced the missile countermeasure. Missile detection is added before scanning for a high-speed flying object. It is built with the assumption that the behavior " Continue to lie down when a missile is detected to 100m range, then jump to avoid after it approach to 20m" . As long as the missile does not come within 20m, it will continue to run the operation of lie down repeatedly. This portion that is run repeatedly, this is the loop. By looping temporarily here, at the moment the missile enters the 20m range, you will be able to perform reaction immediately. To execute the process that you want to run on certain situations quickly, or in order to run an action timely at the moment the situation has changed, loop processing is quite useful. Now tested the program of the sample image, then it was confirmed that it is possible to avoid opponent’s missile on a one-to-one. So I organized a three-machine team triumphantly, and fought with a team that has missiles, then, OMG! There is an OKE that continues to lie down and does not move at all! Of course playing possum like that definitely not effective to OKEs, they were wiped out within a numerical disadvantage. What on earth was the problem? This sample is the form of, "Detected a missile coming towards in the 100m distance " → "loop until a missile is detected in the 20m range" The problem is that, in the first place, it has formed a loop on the assumption that "missile coming towards" is reach to the location of the OKE reliably. The missile coming towards is aimed at the OKE really? Or there is not an obstacle before it reaches? In such a variety of reasons, if the missile did not come in the 20m range, you will not be able to get out of the loop. In this case, you can solve the problem by modifying like the image below. By only one shifting of the ahead of an arrow, you will leave the loop if the missile does not come to 20m range. In the case also maintaining a bidirectional loop, you can resolve the problem as the image below. When you specify the range, you can be outside the range around your OKE by up and down key while holding down R button. By utilizing this, form a loop of “Continue to lie down if there are one or more missiles between 20m and 100m, proceed to avoidance decision when there are no missiles”. In this way, you can perform jump by avoidance decision when the missile is coming within 20m. In addition, even though the missile towards different direction or disappear, loop is always released. (There are waste and problem still in this example, I set it aside for the time being) It was long, but in short, it is that want you to understand firmly the risk and benefits of loop processing. Because bugs of this kind occur frequently, let s repeat behavior test and thoroughly verify when introducing a loop. If you will master successfully, quick reactions become possible in limited situations and that slight differences lead to great results. [Summary] When building a large program, needs attention to the execution timing of behaviors that require quick responses. The more complex and courteous programs, the more reduced the reaction rate is. Beware treatment of unnecessary processes in many cases. Consider the timing that should be executed and the need for each decision. For example, execute a long thinking process during operation that cannot be canceled, etc. Subroutine and loop are useful, but you should utilize it after a solid understanding of its risk. If the subroutine that will be called each time is long, the main program will not go around quickly. Wrong release condition of the loop leads to defeat very likely. [Supplemental Commentary loop examples] Although I gave the missile countermeasure loop as a reference, in addition, describe an example of a relatively safe loop to be able to make easy.Conducting enter and exit of the loop in accordance with the each state of OKE, it will be safety and quick loop process. For example, because it will not be able to perform the most operations when the OKE is struck and overturning, there is a way to check the situation in the dedicated loop and determine whether activate options or not, take evasive action to avoid additional attack immediately after the state recovered. In opposite, if the target is struck and overturning, it might be interesting to enter the loop for pursuit and additional attack. Because the state recovers automatically, it will be expected a certain effect without causing an infinite loop. Narrow down the processes There are many processes that you want to monitor situation changes constantly such as Scan for Projectiles, Activate Option, and process during overturning, etc. You can easily monitor such processes constantly by putting in places to pass frequently (Top of main and top of sub used frequently). However, in other words, would be referred to as "regardless of need or not, have repeated frequently the same process ", it is a waste of processing power. This will cause delaying the response. For example, in the case of Self-Cooling System of options, you do not have to monitor the amount of heat of body constantly in many cases. Mostly the purpose of starting the cooling is either, prevent thermal damage when it is struck or increase the frequency of fire. If the purpose of preventing thermal damage, it is only necessary to assess once when entering or exiting the process of when be struck or avoiding. If you increase the frequency of fire, it is only necessary to assess when it refrain from attack due to the heat. In this way, it is possible to improve the throughput performance if you stop constantly monitor the processes being monitored constantly. However, by stopping the constant monitoring, it is possible that the case that cannot be monitored occurs. In the case of cooling system, if you assess only when entering or exiting the process of when be struck or avoiding, there is likely to be roasted by "beam from close range (undaunted, cannot detect by Scan for Projectiles)" or "heat generated by the flames of napalm (undaunted, are not projectiles )". Although you should assess elsewhere to avoid this, the mounting area increases in this instance, and eventually you would waste the processing power if you assess too much. It is necessary to narrow down and pinpoint the necessary timing of decision, or if you do not narrow, must be determined after having analyzed trade-off among the mounting area, effect and risk when stopped constant monitoring.
https://w.atwiki.jp/dotcom/pages/140.html
Log4Jがなんとなくできそうな気がした(気のせいかも)ので続けてお勉強してみることに。 Appenderってのを使うですよ。いきますよ。 出力先を指定するんです。 つまりコンソールにばっかり出してるだけじゃ能がないってやつをファイルとかに出力したいと思ったのです。 目次 目次 参考資料 とりあえず作ってみる。コピペしてゴー。 うまくいかないので参考サイトをよく読んでみる。 org.apache.log4j.Appender org.apache.log4j.WriterAppender 外部ファイルにログをはきだしたい、を作ってみるテスト・サンプルで試してみる 実行結果！ 何度も実行してもファイルの内容を上書きしない出力方法にしてみる 参考資料 こちらを参考にさせていただいてやってみますよ。 http //www.techscore.com/tech/ApacheJakarta/Log4J/1-2.html とりあえず作ってみる。 やってみないとわからないですはい。 コピペしてゴー。 こういうことなのかしら？って思ってこれで実行してみたの。 コピペしちゃった。手で打たないと覚えないのにね。。。 package Log4Jtest.test.dotcom; import org.apache.log4j.*; public class Log4jTest { public static void main(String argv[]) { Logger logger = Logger.getLogger("Sample"); //Appenderインスタンスの生成 Appender appender = new ConsoleAppender(); logger.addAppender(appender); logger.info("This is info."); } } 実行結果 log4j ERROR No output stream or file set for the appender named [null]. 怒られた(ﾉ▽`) 赤文字でしたよ！ 名前がnullですか。ほう。。。？ そもそもちゃんと理解してるのかい私。 というわけで うまくいかないので参考サイトをよく読んでみる。 先のほうも読んでから実行ないとね。 Appenderについてお勉強しなおし。 org.apache.log4j.Appender インタフェースです。 Loggerに出力するときはこのインタフェースを使うんですね。 私いつもimportで org.apache.log4j.*; って省略してるから気づかなかったわ。 もひとつあるわ。もしかして私がやりたいのってこれ？ org.apache.log4j.WriterAppender こちらはクラス。 OutputStreamとかに出力の時はこっちらしいです。 java.io.*がいりますな。 もしかしてこれじゃん？これ！！！こっちー！ 外部ファイルにログをはきだしたい、を作ってみる 少しだけ利口になったような気がしたのでサンプルを動かしてみます。 テスト・サンプルで試してみる 使わせていただきました。ありがとうございます。 http //www.techscore.com/tech/ApacheJakarta/Log4J/3.html Log4jTestクラスの中をこんな風にしてみた。 public static void main(String argv[]) { //org.apache.log4j.PatternLayoutの生成 PatternLayout layout = new PatternLayout(); //出力ファイル名 String file = "sample.log"; //java.io.Writerオブジェクト //org.apache.log4j.WriterAppenderオブジェクト Writer writer = null; WriterAppender appender = null; try{ writer = new FileWriter(file); appender = new WriterAppender(layout,writer); }catch(IOException e){ } Logger logger = Logger.getLogger("Sample"); logger.addAppender(appender); logger.info("This is info."); System.out.println("おわったよん"); } ファイルに書き出すので実行してもコンソールに何もでない。 それは寂しかったのでとりあえず最後に終わりメッセージを。 java.io.Writerも使うので import java.io.*; も忘れずに。 String file = "sample.log"; 出力ファイル名がファイル名だけ。。。デフォルトで今いる場所に作られるのね。 ってことはEclipseならば、Log4jTestクラスを作ったプロジェクトのフォルダの中にあるってことだ。 workspaceフォルダの下の層を探そう。 そうをさがそう。 ベタなシャレじゃありませんよ。 実行結果！ sample.logを見つけて開いてみると、できてました。 This is info. って入ってました。万歳。 とりあえずこれでできたようだわ。 念のためも一回実行してみよ。。。とおもったら案の定、ファイル上書きされてた(ﾉ▽`) だーよねー。 というわけでちょと形を変えてみたですよ。 何度も実行してもファイルの内容を上書きしない出力方法にしてみる 上の writer = new FileWriter(file); を writer = new FileWriter(file,true); にしてみました。 成功。 これで簡単な形で外部ファイルに書けるようになったわ。 次はフォーマットをきれいにしてみようっと。 じかんとかいれてー。
https://w.atwiki.jp/tmtbnc/pages/60.html
mp4box -h General Options Hinting Options Importing Options MPEG-4 Scene Encoding Options Meta handling Options Extracting Options Dumping Options SWF Importer Options ISMA Encryption/Decryption Options Suppported raw formats and file extensions File Streamer Options mp4box -h MP4Box [option] input [option] -h general general options help -h hint hinting options help -h import import options help -h encode encode options help -h meta meta handling options help -h extract extraction options help -h dump dump options help -h swf Flash (SWF) options help -h crypt ISMA E A options help -h format supported formats help -h rtp streamer help -nodes lists supported MPEG4 nodes -node NodeName gets MPEG4 node syntax and QP info -xnodes lists supported X3D nodes -xnode NodeName gets X3D node syntax -snodes lists supported SVG nodes -snode NodeName gets SVG node syntax -languages lists supported ISO 639 languages -quiet quiet mode -noprog disables progress -v verbose mode -version gets build version General Options -inter time_in_ms interleaves file data (track chunks of time_in_ms) * Note 1 Interleaving is 0.5s by default * Note 2 Performs drift checking accross tracks * Note 3 a value of 0 disables interleaving -old-inter time same as -inter but doesn t perform drift checking -tight performs tight interleaving (sample based) of the file * Note reduces disk seek but increases file size -flat stores file with all media data first, non-interleaved -frag time_in_ms fragments file (track fragments of time_in_ms) * Note Always disables interleaving -ffspace size inserts free space before moof in fragmented files -out filename specifies output file name * Note By default input (MP4,3GP) file is overwritten -tmp dirname specifies directory for temporary file creation * Note Default temp dir is OS-dependent -no-sys removes all MPEG-4 Systems info except IOD (profiles) * Note Set by default whith -add and -cat -no-iod removes InitialObjectDescriptor from file -isma rewrites the file as an ISMA 1.0 AV file -ismax same as -isma and removes all clock references -3gp rewrites as 3GPP(2) file (no more MPEG-4 Systems Info) * Note 1 some tracks may be removed in the process * Note 2 always on for *.3gp *.3g2 *.3gpp -ipod rewrites the file for iPod -psp rewrites the file for PSP devices -brand ABCD[ v] sets major brand of file, with optional version -ab ABCD adds given brand to file s alternate brand list -rb ABCD removes given brand from file s alternate brand list -cprt string adds copyright string to movie -chap file adds chapter information contained in file -rem trackID removes track from file -enable trackID enables track -disable trackID disables track -new forces creation of a new destination file -rem trackID removes track from file -lang [tkID=]LAN sets track language. LAN is the ISO 639-2 code (eng, und) -delay tkID=TIME sets track start delay in ms. -par tkID=PAR sets visual track pixel aspect ratio (PAR=N D or "none") -name tkID=NAME sets track handler name * NAME can indicate a UTF-8 file ("file //file name" -itags tag1[ tag2] sets iTunes tags to file - more info MP4Box -tag-list. -split time_sec splits in files of time_sec max duration * Note this removes all MPEG-4 Systems media -split-size size splits in files of max filesize kB. * Note this removes all MPEG-4 Systems media -split-chunk S E extracts a new file from Start to End (in seconds) * Note this removes all MPEG-4 Systems media -group-add fmt creates a new grouping information in the file. Format is a colon-separated list of following options refTrack=ID ID of the track used as a group reference. If not set, the track will belong to the same group as th e previous trackID specified. If 0 or no previous track specified, a new alternate grou p will be created switchID=ID ID of the switch group to create. If 0, a new ID will be computed for you If 0, disables SwitchGroup criteria=string list of space-separated 4CCs. trackID=ID ID of the track to add to this group. *WARNING* Options modify state as they are parsed trackID=1 criteria=lang trackID=2 is different from criteria=lang trackID=1 trackID=2 -group-rem-track ID removes track from its group -group-rem ID removes the track s group -group-clean removes all group information from all tracks -ref id XXXX refID adds a reference of type 4CC from track ID to track refID -dash dur enables DASH-ing of the file with a segment duration of DU R Note the duration of a fragment (subsegment) is set using the interleaver (-inter) s witch. Note You can specify -rap switch to split segments at RA P boundaries -frags-per-sidx N sets the number of segments to be written in each SIDX box If 0, SIDX box is not used -segment-name name sets the segment name for generated segments If not set (default), segments are concatenated in output file -segment-ext name sets the segment extension. Default is m4s -url-template uses UrlTemplate instead of explicit sources in segments. Ignored if segments are stored in the output file. Hinting Options Hinting Options -hint hints the file for RTP/RTSP -mtu size specifies RTP MTU (max size) in bytes. Default size is 145 0 * Note this includes the RTP header (12 bytes) -copy copies media data to hint track rather than reference * Note speeds up server but takes much more space -multi [maxptime] enables frame concatenation in RTP packets if possible maxptime max packet duration in ms (optional, default 100ms) -rate ck_rate specifies rtp rate in Hz when no default for payload * Note default value is 90000 (MPEG rtp rates) -mpeg4 forces MPEG-4 generic payload whenever possible -latm forces MPG4-LATM transport for AAC streams -static enables static RTP payload IDs whenever possible * By default, dynamic payloads are always used MPEG-4 Generic Payload Options -ocr forces all streams to be synchronized * Most RTSP servers only support synchronized streams -rap signals random access points in RTP packets -ts signals AU Time Stamps in RTP packets -size signals AU size in RTP packets -idx signals AU sequence numbers in RTP packets -iod prevents systems tracks embedding in IOD * Note shouldn t be used with -isma option -add-sdp string adds sdp string to (hint) track ("-add-sdp tkID string") or movie. This will take care of SDP lines ordering -unhint removes all hinting information. Importing Options Importing Options File importing syntax "#video" "#audio" base import for most AV files "#trackID=ID" track import for IsoMedia and other files "#pid=ID" stream import from MPEG-2 TS " dur=D" imports only the first D seconds " lang=LAN" sets imported media language code " delay=delay_ms" sets imported media initial delay in ms " par=PAR" sets visual pixel aspect ratio (PAR=Num Den) " name=NAME" sets track handler name " ext=EXT" overrides file extension when importing " hdlr=code" sets track handler type to the given code point (4CC) " disable" imported track(s) will be disabled " group=G" adds the track as part of the G alternate group. If G is 0, the first available GroupID will be picked. " fps=VAL" same as -fps option " agg=VAL" same as -agg option " par=VAL" same as -par option " dref" same as -dref option " nodrop" same as -nodrop option " packed" same as -packed option " sbr" same as -sbr option " sbrx" same as -sbrx option " ps" same as -ps option " psx" same as -psx option " ovsbr" same as -ovsbr option " mpeg4" same as -mpeg4 option " font=name" specifies font name for text import (default "Serif") " size=s" specifies font size for text import (default 18) " stype=4CC" forces the sample description type to a different value !! THIS MAY BREAK THE FILE WRITING !! " chap" specifies the track is a chapter track " profile" forces the profile for the H.264 content - high444, high, extended, main, baseline *WARNING* wrong value may cause playback issue " compat" forces the profile compatibity flags for the H.264 content *WARNING* wrong value may cause playback issue " level" forces the level for the H.264 content *Note If value 6, interpreted as decimal expression " vidformat" forces the video_format flag in VUI for the H.264 content - component, pal, ntsc, secam, mac, undef " fullrange" forces the video_full_range_flag in VUI for the H.264 cont ent - on, off " colorprim" forces the colour_primaries flag in VUI for the H.264 cont ent - bt709, undef, bt470m, bt470bg, smpte170m, smpte240m, film " transfer" forces the transfer_characteristics flag in VUI for the H. 264 content - bt709, undef, bt470m, bt470bg, smpte170m, smpte240m, linear log100, log316 " colmatrix" forces the matrix_coefficients flag in VUI for the H.264 c ontent - GBR, bt709, undef, fcc, bt470bg, smpte170m, smpte240m , YCgCo " layout=WxHxXxY" specifies the track layout - if W (resp H) = 0, the max width (resp height) of the tracks in the file are used. - if Y=-1, the layout is moved to the bottom of the track area - X and Y can be omitted ( layout=WxH) -add file add file tracks to (new) output file -cat file concatenates file samples to (new) output file * Note creates tracks if needed -force-cat skips media configuration check when concatenating file !!! THIS MAY BREAK THE CONCATENATED TRACK(S) !!! -keep-sys keeps all MPEG-4 Systems info when using -add / cat -keep-all keeps all existing tracks when using -add * Note only used when adding IsoMedia files All the following options can be specified as default or for each track. When specified by track the syntax is " opt" or " opt=val". -dref keeps media data in original file -no-drop forces constant FPS when importing AVI video -packed forces packed bitstream when importing raw ASP -sbr backward compatible signaling of AAC-SBR -sbrx non-backward compatible signaling of AAC-SBR -ps backward compatible signaling of AAC-PS -psx non-backward compatible signaling of AAC-PS -ovsbr oversample SBR * Note SBR AAC, PS AAC and oversampled SBR cannot be d etected at import time -fps FPS forces frame rate for video and SUB subtitles import FPS is either a number or expressed as timescale-increm ent * For raw H263 import, default FPS is 15 * For all other imports, default FPS is 25 !! THIS IS IGNORED FOR IsoMedia IMPORT !! -mpeg4 forces MPEG-4 sample descriptions when possible (3GPP2) For AAC, forces MPEG-4 AAC signaling even if MPEG-2 -agg N aggregates N audio frames in 1 sample (3GP media only) * Note Maximum value is 15 - Disabled by default MPEG-4 Scene Encoding Options MPEG-4 Scene Encoding Options -mp4 specify input file is for encoding. -def encode DEF names -sync time_in_ms forces BIFS sync sample generation every time_in_ms * Note cannot be used with -shadow -shadow time_ms forces BIFS sync shadow sample generation every time_ms. * Note cannot be used with -sync -log generates scene codec log file if available -ms file specifies file for track importing Chunk Processing -ctx-in file specifies initial context (MP4/BT/XMT) * Note input file must be a commands-only file -ctx-out file specifies storage of updated context (MP4/BT/XMT) LASeR Encoding options -resolution res resolution factor (-8 to 7, default 0) all coords are multiplied by 2^res before truncation -coord-bits bits bits used for encoding truncated coordinates (0 to 31, default 12) -scale-bits bits extra bits used for encoding truncated scales (0 to 4, default 0) -auto-quant res resolution is given as if using -resolution but coord-bits and scale-bits are infered Meta handling Options Meta handling Options -set-meta args sets given meta type - syntax "ABCD[ tk=ID]" * ABCD four char meta type (NULL or 0 to remove meta) * [ tk=ID] if not set use root (file) meta if ID is 0 use moov meta if ID is not 0 use track meta -add-item args adds resource to meta * syntax file_path + options ( separated) tk=ID meta adressing (file, moov, track) name=str item name mime=mtype item mime type encoding=enctype item content-encoding type * file_path "this" or "self" item is the file itself -rem-item args removes resource from meta - syntax item_ID[ tk=ID] -set-primary args sets item as primary for meta - syntax item_ID[ tk=ID] -set-xml args sets meta XML data * syntax xml_file_path[ tk=ID][ binary] -rem-xml [tk=ID] removes meta XML data -dump-xml args dumps meta XML to file - syntax file_path[ tk=ID] -dump-item args dumps item to file - syntax item_ID[ tk=ID][ path=fileName ] -package packages input XML file into an ISO container * all media referenced except hyperlinks are added to fil e Extracting Options Extracting Options -raw TrackID extracts track in raw format when supported -raws TrackID extract each track sample to a file * Note "TrackID N" extracts Nth sample -nhnt TrackID extracts track in nhnt format -nhml TrackID extracts track in nhml format (XML nhnt). * Note "-nhml +TrackID" for full dump -single TrackID extracts track to a new mp4 file -avi TrackID extracts visual track to an avi file -qcp TrackID same as -raw but defaults to QCP file for EVRC/SMV -aviraw TK extracts AVI track in raw format $TK can be one of "video" "audio" "audioN" -saf remux file to SAF multiplex -dvbhdemux demux DVB-H file into IP Datagrams * Note can be used when encoding scene descriptions -diod extracts file IOD in raw format when supported Dumping Options Dumping Options -std dumps to stdout instead of file -info [trackID] prints movie info / track info if trackID specified * Note for non IsoMedia files, gets import options -bt scene to bt format - removes unknown MPEG4 nodes -xmt scene to XMT-A format - removes unknown MPEG4 nodes -wrl scene VRML format - removes unknown VRML nodes -x3d scene to X3D/XML format - removes unknown X3D nodes -x3dv scene to X3D/VRML format - removes unknown X3D nodes -lsr scene to LASeR format -diso scene IsoMedia file boxes in XML output -drtp rtp hint samples structure to XML output -dts prints sample timing to text output -sdp dumps SDP description of hinted file -dcr ISMACryp samples structure to XML output -dump-cover Extracts cover art -dump-chap Extracts chapter file -ttxt Converts input subtitle to GPAC TTXT format -ttxt TrackID Dumps Text track to GPAC TTXT format -srt Converts input subtitle to SRT format -srt TrackID Dumps Text track to SRT format -stat generates node/field statistics for scene -stats generates node/field statistics per MPEG-4 Access Unit -statx generates node/field statistics for scene after each AU -hash generates SHA-1 Hash of the input file SWF Importer Options SWF Importer Options MP4Box can import simple Macromedia Flash files (".SWF") You can specify a SWF input file with -bt , xmt and -mp4 options -global all SWF defines are placed in first scene replace * Note By default SWF defines are sent when needed -no-ctrl uses a single stream for movie control and dictionary * Note this will disable ActionScript -no-text removes all SWF text -no-font removes all embedded SWF Fonts (terminal fonts used) -no-line removes all lines from SWF shapes -no-grad removes all gradients from swf shapes -quad uses quadratic bezier curves instead of cubic ones -xlp support for lines transparency and scalability -flatten ang complementary angle below which 2 lines are merged * Note angle 0 means no flattening ISMA Encryption/Decryption Options ISMA Encryption/Decryption Options -crypt drm_file crypts a specific track using ISMA AES CTR 128 -decrypt [drm_file] decrypts a specific track using ISMA AES CTR 128 * Note drm_file can be omitted if keys are in file -set-kms kms_uri changes KMS location for all tracks or a given one. * to adress a track, use tkID=kms_uri DRM file syntax for GPAC ISMACryp File is XML and shall start with xml header File root is an "ISMACryp" element File is a list of "ISMACrypTrack" elements ISMACrypTrack attributes are TrackID ID of track to en/decrypt key AES-128 key formatted (hex string 0x +32 chars) salt CTR IV salt key (64 bits) (hex string 0x +16 chars) Encryption only attributes Scheme_URI URI of scheme used KMS_URI URI of key management system * Note self writes key and salt in the file selectiveType selective encryption type - understood values are "None" all samples encrypted (default) "RAP" only encrypts random access units "Non-RAP" only encrypts non-random access units "Rand" random selection is performed "X" Encrypts every first sample out of X (uint) "RandX" Encrypts one random sample out of X (uint) ipmpType IPMP Signaling Type None, IPMP, IPMPX ipmpDescriptorID IPMP_Descriptor ID to use if IPMP(X) is used * If not set MP4Box will generate one for you Suppported raw formats and file extensions Suppported raw formats and file extensions NHNT .media .nhnt .info NHML .nhml (opt .media .info) MPEG-1-2 Video .m1v .m2v MPEG-4 Video .cmp .m4v H263 Video .263 .h263 AVC/H264 Video .h264 .h26L .264 .26L JPEG Images .jpg .jpeg PNG Images .png MPEG 1-2 Audio .mp3, .m1a, .m2a ADTS-AAC Audio .aac AMR(WB) Audio .amr .awb EVRC Audio .evc SMV Audio .smv Supported containers and file extensions AVI .avi MPEG-2 PS .mpg .mpeg .vob .vcd .svcd MPEG-2 TS .ts .m2t QCP .qcp OGG .ogg ISO-Media files no extension checking Supported text formats SRT Subtitles .srt SUB Subtitles .sub GPAC Timed Text .ttxt QuickTime TeXML Text .xml (cf QT documentation) Supported Scene formats MPEG-4 XMT-A .xmt .xmta .xmt.gz .xmta.gz MPEG-4 BT .bt .bt.gz VRML .wrl .wrl.gz X3D-XML .x3d .x3d.gz X3D-VRML .x3dv .x3dv.gz MacroMedia Flash .swf (very limitted import support only) File Streamer Options File Streamer Options MP4Box can stream ISO files to RTP. The streamer currently doesn t support data carrouselling and will therefore not handle BIFS and OD streams properly. -rtp enables streamer -noloop disables looping when streaming -mpeg4 forces MPEG-4 ES Generic for all RTP streams -dst=IP IP destination (uni/multi-cast). Default 127.0.0.1 -port=PORT output port of the first stream. Default 7000 -mtu=MTU path MTU for RTP packets. Default is 1450 bytes -ifce=IFCE IP address of the physical interface to use. Default NULL (ANY) -ttl=TTL time to live for multicast packets. Default 1 -sdp=Name file name of the generated SDP. Default "session.sdp"
https://w.atwiki.jp/bubublender/pages/18.html
Fileメニュー New Open Open Recent Recover Last Session Save Save as Compress File Save Image... Dump SubWindow Dump Screen Save Runtime... Save Dynamic Runtime... Save Default Settings 設定したレイアウトを保存します。 Load Factory Settings レイアウトを初期化します。 Append or Link Import Export Pack Data Unpack Date... Quit Blender
https://w.atwiki.jp/vocaloidenglishlyric/pages/822.html
【Tags Miku tL yusukeP L】 Original Music title Life Stream Romaji music title Life Stream Music Lyrics written, Voice edited by yusukeP Music arranged by yusukeP Singer(s) 初音ミク (Hatsune Miku) Click here for the original Japanese Lyrics Romaji lyrics (transliterated by motokokusanagi2009)： sotto toke dashi te iku zutto nagare tsuzukeru hoshi no naka no inori kibō inochi no ato sotto gyutto daki yose afure dashita inochi no rasen hitotsu hito shizuku No reason for you nagare ochita hoshikuzu wa iro o kae te hikari tomosu yōni atarashī toki o rasen eto nose te sotto inori tsuzuke te zutto negai tsuzuke te hoshi no kodomo tachi wa kibō katari akasu daichi no kiseki yo koboreru ai chīsa na te shinjitsu o tsukami toru No reason for you todomaru koto o shirazu ni toki wa sugi te hikari tsuzukeru yo inochi no hoshi wa mawari yuku inorō nagare ochita hoshikuzu wa iro o kae te utaō towa no uta o [yusukeP, yusuke-P]
https://w.atwiki.jp/xbox360score/pages/2311.html
Field Stream Total Outdoorsman Challenge 項目数：47 総ポイント：1000 難易度： ※リージョンロックあり。北米版は北米の、欧州版は欧州の本体が必要。 欧州版(All Round Hunter)は別実績。 Basic Huting Skills move around a level 10 Get to know Bag 1 animal 10 Elk on the loose Hunt 2 elk 10 Looks real to me Hunt any animal by using a decoy 10 Trophy collector You filled your trophy room 15 Night hunter Hunt 2 of each night animal 15 Marksman Level 1 Shoot one animal using any shotgun 20 Hunting Frenzy Hunt 10 animals 20 ultimate Hunter complete all missions from any environment 30 Complete Hunter Hunt 1 of each animal type 30 Missions Man finish one mission on normal difficulty 10 Top gun finish one mission on realistic difficulty 20 Early fall hunter Finish all missions from the early fall environment 30 British Columbia Hunter Finish all missions form British Columbia Early Fall 30 Winter Hunter Finish all missions form the winter environment 30 Fall hunter Finish all mission form the fall environment 30 Competitive hunter Play your first multi player game 10 Firearms collection unlock all firearms 30 Fashion victim unlock all types of clothing 20 Duck hunter Hunt 10 ducks using a shotgun 15 Blind hunt Hunt one animal from a blind 25 Mission accomplished Win all the missions 40 Animal party Unlock all the animals. 40 Best hunter Win your first multi player game 40 Better luck next time Lose your first multi player game 20 Cats in the bag Hunt every type of cat (Bobcat, Lynx,) 30 Im the best Win all missions from multi-player mode 30 Moose fanatic fill your trophy room with Moose mounts 20 Zero magnification Win a mission without using any scope or Binoculars 30 Inspector Inspect your first track 30 Call to arms Hunt any animal by calling it to your location 30 Revolver Hunt any animal using the handgun 20 Rabbit Race Collect your first trophy 10 Rabbit s foot Kill 10 rabbits using any allowed firearm 20 Rules and Regulation Hunt 10 times without breaking any rules 20 Don t just stand there, shoot. Hunt 5 animals from a stand 20 Fox trot Put 10 foxes in your trophy room 30 Grouse hunter Hunt 5 Grouse 10 Turkey shoot Hunt 5 turkeys 10 Odor-free Use all the scent items in the game 30 Sheep double Hunt one bighorn sheep and one Dall sheep 10 Learn to track Track down you first animal 10 This is my turf Win all the missions form early fall environment in multi player 20 Sixth sense Enter Sixth Sense for the first time 10 Lure the animals Use all the lures(including decoys and bait). 10 Get a tail feather Hunt 10 pheasants 20 Gearing up Unlock all items 20
https://w.atwiki.jp/matchmove/pages/80.html
File Menu 多くのエントリは、Windows-標準です。たとえば、File/Newはシーンをクリアし、Shot/Add Shotダイアログを開始します。 File/Merge 現在開いているファイルに前もって保存したSynthEyesの.sniシーンファイルをマージします、ショット、オブジェクト、トラッカー、メッシュ、その他を含みます。ほとんどの要素は衝突を避けるために独自の名前を自動的に割り当てられます。ただし、ダイアログボックスでトラッカーに独自の名前を割り当てるか選択できます。 File/Import/Shot シーンをクリアし、既存のショットがないならば、Shot/Add Shotダイアログが開きます、または、一つ以上のショットがすでに存在するならば、さらなるショットを加えます。 File/Import/Mesh DXFまたはAlias/Wavefront OBJをtest objectとしてメッシュインポートします。 File/Import/Tracker Locations x_value, y_value, z_value, Tracker_nameの行から成るテキストファイルをインポートします。行ごとに、既存のトラッカーがその名前ならば、その位置は与えられる座標にセットされます。その名前のトラッカーがいないならば、新しいトラッカーが指定された座標系で作成されます。たとえば既存のオブジェクトモデルやset measurements？からseed locationsのセットをインポートするために使ってください。 それが開いているならば、新しいトラッカーはトラッカーパネルからのセッティングを使います。merging files（ファイルを合併する）に関するセクションを参照してください。 File/Import/Extra Points x、y、z値（各行のオプションポイント名の前後は任意です）の行から成るテキストファイルをインポートします。 ヘルパーポイントは、行ごとに作成されます。たとえば、ポイントは測量によって決定されたかもしれません？。 このオプションで、ポイントを比較して見ることができます。merging files（ファイルを合併する）に関するセクションを参照してください。 Export Again 前回行ったCGアプリケーションへのエクスポート動作を再度行います。 Find New Scripts SynthEyes起動後にスクリプトフォルダに置かれた新スクリプトをSynthEyesに配置させ、スクリプトを動作できるようにします。 File Info カレントファイルのフルパスファイルネーム、作成タイムスタンプ、最終更新タイムスタンプ、 全ロードショットのフルパスファイルネーム、全インポートメッシュのファイルネーム（およびインポートタイムスタンプ）を表示します。 加えて、Descriptionにはファイルに格納されるあなた固有の図形情報を加えることができます。 User Data Folder 設定、バッチ、スクリプト、ダウンロード、プレビュームービーフォルダ、その他を含むフォルダを開きます。 Submit for batch 現在のシーンは、待ち行列エリアに書き込むことによって、バッチ処理になります。バッチ処理が走るまで、またはその前のジョブがなくなるまでそれは処理されません。 Batch Process SynthEyesはバッチ処理ウインドウを開けて、待ち行列内の全ジョブを処理し始めます。 Batch Input Queue Windows Explorerを開き、待ち行列フォルダにバッチ処理をインプットします。待ち行列は確認・削除・追加できます。 Batch Output Queue Windows Explorerを開き、待ち行列フォルダにバッチ処理をアウトプットします。完了したジョブの確認・移動ができます。 Exporter Outputs Windows Explorerをデフォルトエクスポートフォルダで開きます。